-
Notifications
You must be signed in to change notification settings - Fork 730
feat(amazonq): enable pre flare experiment #7999
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
| const inlineChatTutorialAnnotation = new InlineChatTutorialAnnotation(inlineTutorialAnnotation) | ||
|
|
||
| const enableInlineRollback = true | ||
| const enableInlineRollback = FeatureConfigProvider.instance.getPreFlareRollbackGroup() === 'treatment' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
when this line of code is invoked at the activation phrase, the feature config API has not been called and it won't know if it is treatment or not.
Can you do this:
- In the FeatureConfig provider, when it call getPreFlareRollbackGroup. If there is API response, if this response is not the same as disk cache, override disk cache. If the response is the same as disk cache. do nothing. If this
getPreFlareRollbackGroupis called even before the listFeatureEvaluation API call, then just return from the cache.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I setup debug mode and it was called before this line, let me double check again
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2025-09-08 18:51:01.940 [info] AB Testing Cohort Assignments [
{
feature: 'PreflareRollbackExperiment_BID',
variation: 'CONTROL',
value: { stringValue: 'CONTROL' }
}
]
2025-09-08 18:51:01.940 [debug] CodeWhisperer: Current feature configs: {PreflareRollbackExperiment_BID: CONTROL}
2025-09-08 18:51:03.182 [info] Command: (not started) [/Users/yuxqiang/Library/Caches/aws/toolkits/language-servers/AmazonQ/1.31.0/servers/node --inspect=6080 --max-old-space-size=8196 /Users/yuxqiang/Library/Caches/aws/toolkits/language-servers/AmazonQ/1.31.0/servers/aws-lsp-codewhisperer.js --nolazy --preserve-symlinks --stdio --pre-init-encryption --set-credentials-encryption-key] (running processes: 1)
2025-09-08 18:51:04.014 [debug] amazonqLsp: Fetching config section aws.q for language server
2025-09-08 18:51:04.014 [debug] amazonqLsp: Fetching config section aws.q for language server
2025-09-08 18:51:04.380 [debug] codewhisperer: new user login, activating inline tutorial. (autotriggerEnabled=true; inlineState=amazonq_annotation_inline_chat)
2025-09-08 18:51:04.380 [info] Entering postflare logic
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also:
// This contains every lsp agnostic things (auth, security scan, code scan)
await activateCodeWhisperer(extContext as ExtContext)
if (!isAmazonLinux2() || hasGlibcPatch()) {
// Activate Amazon Q LSP for everyone unless they're using AL2 without the glibc patch
await activateAmazonqLsp(context)
}
activateCodeWhisperer will call fetchFeatureConfig once at the end, activateAmazonqLsp will deterine whether it goes the preflare or post flare path.
Problem
Solution
feature/xbranches will not be squash-merged at release time.